Open
Conversation
Switching from Yarn to npm as the sole package manager. The lock file will be replaced by package-lock.json. Co-Authored-By: Claude Opus 4.6 <[email protected]>
No longer needed since the project uses npm exclusively. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Generated by npm install to replace yarn.lock as the dependency lock file. Co-Authored-By: Claude Opus 4.6 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
yarn.lockin favor ofpackage-lock.jsonyarn-error.logfrom.gitignore(no longer relevant)Context
The project had a
yarn.lockfile but the README and CI already referencednpm install. This PR completes the migration to npm as the sole package manager, removing the inconsistency.Test plan
npm installcompletes successfullynpm run build(webpack encore production) compiles without errors🤖 Generated with Claude Code